Method and system of recovering lost mobile devices

ABSTRACT

An approach is provided for remotely controlling and/or tracking mobile devices. A request is received to track a mobile device. A control signal is generated, in response to the request, to remotely activate an application on the mobile device for controlling an audio interface or an imaging interface of the mobile device to capture a signal from the audio interface or the imaging interface.

BACKGROUND INFORMATION

Consumer adoption of mobile devices, such as cellular telephones, laptopcomputers, pagers, personal digital assistants, and the like, isincreasing. These devices can be used for a diversity of purposesranging from basic communications, to conducting business transactions,to managing entertainment media, as well as a host of other tasks.Additional enhancements, such as location-awareness features, e.g.,global positioning system (GPS) tracking, also enable mobile deviceusers to monitor their position and present their location via a localdisplay. As such, mobile devices tend to store an abundant amount ofpersonal or otherwise sensitive information. Unfortunately, theportability and size of these devices often leads to devicemisplacement, loss, and even theft, all of which translate into aninability to safeguard this personal information. In the event that auser's mobile device does go missing (for whatever the cause), thelikelihood of locating and retrieving the device or determining theidentity of a potential perpetrator is very low.

Therefore, there is a need for an approach that can efficiently andeffectively provide remote mobile device control and tracking.

BRIEF DESCRIPTION OF THE DRAWINGS

Various exemplary embodiments are illustrated by way of example, and notby way of limitation, in the figures of the accompanying drawings inwhich like reference numerals refer to similar elements and in which:

FIG. 1 is a diagram of a system configured to provide remote control andtracking services for mobile devices, according to an exemplaryembodiment;

FIG. 2 is a diagram of a platform capable of providing remote controland tracking services for mobile devices, according to an exemplaryembodiment;

FIG. 3 is a diagram of a mobile device configured to facilitate remotecontrol and tracking services, according to an exemplary embodiment;

FIG. 4 is a flowchart of a process for subscribing a user to remotecontrol and tracking services for mobile devices, according to anexemplary embodiment;

FIGS. 5A and 5B are flowcharts of processes for remotely tracking amobile device, according to exemplary embodiments;

FIG. 6 is a graphical user interface for remotely tracking a mobiledevice, according to an exemplary embodiment;

FIGS. 7A and 7B are flowcharts of processes for remotely controlling orconfiguring a mobile device, according to exemplary embodiments;

FIG. 8 is a graphical user interface for remotely controlling orconfiguring a mobile device, according to an exemplary embodiment;

FIG. 9 is a flowchart of a process for providing tracking informationrelated to a mobile device to an administrative agency, according to anexemplary embodiment; and

FIG. 10 is a diagram of a computer system that can be used to implementvarious exemplary embodiments.

DESCRIPTION OF THE PREFERRED EMBODIMENT

A preferred apparatus, method, and software for providing remote controland tracking services for mobile devices are described. In the followingdescription, for the purposes of explanation, numerous specific detailsare set forth in order to provide a thorough understanding of thepreferred embodiments of the invention. It is apparent, however, thatthe preferred embodiments may be practiced without these specificdetails or with an equivalent arrangement. In other instances,well-known structures and devices are shown in block diagram form inorder to avoid unnecessarily obscuring the preferred embodiments of theinvention.

Although various exemplary embodiments are described with respect toremotely controlling and tracking mobile devices to protect againsttheft and to enable recovery, it is contemplated that various exemplaryembodiments are also applicable to stationary devices as well as otherapplications.

FIG. 1 is a diagram of a system configured to provide remote control andtracking services for mobile devices, according to an exemplaryembodiment. For the purpose of illustration, system 100 for remotelycontrolling and tracking one or more mobile devices 101, such as one ormore cellular phones, is described with respect to management platform(or platform) 103. According to certain embodiments, users at user orclient devices (e.g., computing device 105, voice station 107, oranother mobile device (not shown)) may access the features andfunctionalities of platform 103 over one or more networks, such as datanetwork 109, service provider network 111, telephony network 113, and/orwireless network 115, in order to remotely determine and monitor thelocation and/or surrounding environment of their mobile devices 101when, for instance, the users misplace (or otherwise lose) these devices101. Additionally (or alternatively), platform 103 may enable users toremotely control mobile devices 101 in order to, for example, backup orerase a memory (not shown), capture signals from an interface (e.g.,audio interface, imaging interface, etc.), configure (or reconfigure)functions, obtain usage logs, terminate services, etc., of or associatedwith these devices 101. While specific reference will be made hereto, itis contemplated that system 100 may embody many forms and includemultiple and/or alternative components and facilities.

It is observed that portable device users who enjoy an increased levelof mobility have to be mindful of their location, as well as keep avigilant eye on their devices to ensure the devices and/or informationstored thereon is not misplaced, lost, or stolen. Traditionally, when aportable device went missing, for whatever the cause, the use ofconventional approaches to locate and recover the device or, at least,identify a potential perpetrator, e.g., a thief, has yielded little, ifany, success. Moreover, most mobile device owners rely on password andencryption techniques to protect valuable or otherwise sensitiveinformation stored to their devices; however, even encrypted data, oncein the hands of another, may be eventually decrypted. As a consequence,a void exists in the marketplace for effective and efficient techniquesto remotely control and track mobile devices, such as for the purpose oflocating and recovering missing devices or identifying potentialperpetrators.

Therefore, the approach of system 100, according to certain exemplaryembodiments, stems from the recognition that consumers can benefit fromremote control and tracking services, whereby subscribers (or users) aregiven access to a management platform for remotely activating at leastone application on their devices, such as one or more mobile devices,for locating and/or controlling these devices. For instance, subscribersmay access the management platform for remotely activating anapplication on a mobile device for controlling an audio interface (e.g.,a microphone) and/or an imaging interface (e.g., a camera) of the mobiledevice to capture one or more signals from the audio interface or theimaging interface. Captured signals may relate to acoustic and/or visualindicia of an environment surrounding the mobile device, which may beutilized by a subscriber to locate and retrieve their device or identifya potential perpetrator who may have stolen or inadvertently takenpossession of the device. In other instances, remotely activating anapplication on the mobile device may cause the mobile device to returnspatial positioning information (e.g., an address, latitude, longitude,elevation, etc.) corresponding to a location of the device. This spatialpositioning information may be overlaid on, for instance, a topologicaldepiction of a geographic area surrounding the location of the device,which may also be appended with various cartographic features, such asbuildings, landmarks, roadways, signs, and the like, or provided withdirections to the location of the device. Subscribers may also be givenaccess to the management platform to remotely activate at least oneapplication on their device to control or configure one or more featuresof the device. For example, an application may be remotely activated inorder to image (or backup) a memory of a mobile device, as well as storethe image to, for instance, a networked repository. Subscribers may alsobe enabled to erase a memory of the mobile device, such as for thepurpose of purging the device of personal or otherwise sensitiveinformation. Still further, an application may be remotely activated inorder to configure features of or services available to the mobiledevice, such as to monitor or deactivate an ability of the mobile deviceto transmit and receive information.

Accordingly, in some embodiments, system 100 facilitates remote mobiledevice controlling and tracking by enabling subscribers (or users) toaccess management platform 103 via one or more client devices (e.g.,computing device 105, voice station 107, or another mobile device (notshown)) to register to the remote control and tracking services ofsystem 100, as well as to create, customize, and manage one or more userprofiles stored to, for example, user profiles repository 117 or anyother suitable storage location of (or accessible to) the components orfacilities of system 100. In this manner, subscribers may submitrequests to platform 103 in order to remotely control, configure,monitor, register, and/or track their mobile devices 101. In responsethereto, platform 103 may generate one or more control signals toremotely activate one or more applications (or application programminginterfaces (API)) 119 on mobile devices 101 for remotely controlling,configuring, monitoring, and/or tracking these devices 101. Controlsignals may be transmitted to mobile devices 101 over one or more ofnetworks 109-115, such as transmitted over one or more of networks109-115 as part of one or more API 119 directed messages (e.g., API 119short messaging service (SMS) directed messages). It is noted thatmanagement platform 103 is described in more detail in accordance withFIG. 2.

In certain exemplary embodiments, access to platform 103 may be obtainedvia any suitable portal interface (not illustrated), such as a voiceportal or a web portal. For example, a networked remote application 121for implementing the portal may be deployed via platform 103; however,it is contemplated that another facility or component of system 100,such as a frontend, middleware, or backend server, may deploy remoteapplication 121 and, consequently, interface with platform 103. As such,it is contemplated that remote application 121 may be implemented on oneor more of client devices 101, 105, and/or 107 and, thereby, configuredto interface with platform 103. In certain embodiments, one or moreremote applications 121 may function in conjunction with one another toachieve the features and functionalities of system 100, such as one ormore of the processes described herein for remotely controlling and/ortracking mobile devices 101.

The portal may include or provide users with the ability to access,configure, manage, and store user profile information to user profilesrepository 117, as well as the ability to remotely control, configure,monitor, and/or track their mobile devices 101. As such, platform 103may be configured to receive or retrieve tracking content from mobiledevices 101 and, thereby, store this tracking content to, for example,tracking content repository 123. It is contemplated that trackingcontent may be additionally (or alternatively) stored to any othersuitable storage location or memory of (or accessible to) the componentsor facilities of system 100. Further, tracking content may generallyrelate to any signals or information retrieved (or received) from mobiledevices 101 that have been (or currently are being) remotely controlled,configured, monitored, tracked, etc. In this manner, the portal mayprovide subscribers with access to tracking content of tracking contentrepository 123.

As seen in FIG. 1, platform 103 includes remote application 121 forgenerating commands, instructions, parameters, and/or signals(hereinafter collectively referred to as “control signals”) that may beexecuted on (or by) mobile device 101 via API(s) 119. These controlsignals are utilized to remotely activate API(s) 119 to control,configure, monitor, or track mobile device 101 in response to, forinstance, a request to control, configure, monitor, or track mobiledevice 101 by an authorized subscriber of the remote control andtracking services of system 100. In this manner, the control signals maybe utilized to generate, store, or otherwise implement configurationinformation based on received control signal(s). According to oneembodiment, control signals may also be utilized to control an audiointerface (e.g., a microphone) or an imaging interface (e.g., a camera)of mobile device 101 to capture one or more signals from the audiointerface or the imaging interface. Captured signals may relate toacoustic and/or visual indicia of an environment surrounding mobiledevice 101, which may be utilized by a subscriber to locate and retrievetheir device or identify a potential perpetrator who may have stolen orinadvertently taken possession of the device.

In other instances, remote application 121 may generate control signalsto remotely activating API(s) 119 on mobile device 101 to cause mobiledevice 101 to return spatial positioning information (e.g., an address,latitude, longitude, elevation, etc.) corresponding to a location ofmobile device 101. Accordingly, mobile device 101 may be configured todetermine corresponding spatial positioning information throughconventional satellite positioning system (SPS) technology, such as GPStechnology; however, any suitable navigational or location determinationtechnology may be utilized, such as advanced forward link trilateration(A-FLT), assisted-GPS (A-GPS), enhanced cellular identification(CELL-ID), wireless area network (WLAN) positioning, etc. As is wellknown, SPS technology utilizes a constellation 125 of satellites thattransmit signals to receivers (not shown) of, for example, one or moremobile devices 101, so that the receivers may determine correspondingspatial positions (or locations), speeds, directions, and/or timing formobile devices 101. Mobile devices 101 may report this information toplatform 103 to facilitate the remote control and/or tracking servicesof system 100. It is also noted that platform 103 may “poll” or receivesuch spatial positioning information from mobile devices 101 inreal-time, so as to provide presence service features related to mobiledevices 101. As such, the location of, for instance, mobile device 101may be detected without mobile device 101 having to initiate a phonecall or other like communication session. Thus, platform 103 may beconfigured to present received and/or retrieved spatial positioninginformation to subscribers, such as via one or more GUI(s). It is alsonoted that spatial positioning information may be stored to userprofiles repository 117 or any other suitable storage location or memoryof (or accessible to) system 100.

Accordingly to particular embodiments, spatial positioning informationcorresponding to a location of mobile device 101 may be overlaid on, forinstance, a topological depiction of a geographic area surrounding thelocation of mobile device 101, which may also be appended with variouscartographic features, such as buildings, landmarks, roadways, signs,and the like, or provided with directions to the location of mobiledevice 101.

Subscribers may also be given access to the management platform toremotely activate API(s) 119 on mobile devices 101 to control orconfigure one or more features of the device. For example, API(s) 119may be remotely activated in order to image (or backup) a memory (notshown) of mobile device 101, as well as store the image to, forinstance, a networked repository, such as tracking content repository123. Subscribers may also be enabled to erase a memory of mobile device101, such as for the purpose of purging mobile device 101 of personal orotherwise sensitive information. Still further, API(s) 119 may beremotely activated to configure features of or services available tomobile device 101, such as to monitor or deactivate an ability of mobiledevice 101 to transmit and receive information. For instance, controlsignals may be transmitted to mobile device 101 by platform 103 in orderto “lock” mobile device 101 until an appropriate “unlock” code (orsignal) is input (or transmitted) to device 101. As another example,subscribers may be enabled to request platform 103 to monitor usage ofmobile device 101 and, thereby, provide a “log” of such use, which mayalso enable subscribers to determine whether or not their devices havebeen stolen and/or being utilized for illicit (or otherwiseunauthorized) purposes.

Accordingly, platform 103 via, for example, remote application 121 maybe configured to issue control signals via various bearers to mobiledevices 101, such as in the form of one or more call control setupmessages, short messaging service (SMS) messages, enhanced messagingservice (EMS) messages, multimedia messaging service (MMS) messages,electronic mail, files, or any other suitable bearer, as well as anysuitable combination thereof. In particular implementations, thesebearer mediums may include control signals in various forms, includingattention (AT) commands, menu traversal paths, function codes, voicedata, dual-tone multi-frequency (DTMF) signals, scripts, strings,parameters, object variables, and the like. It is noted that thesecontrol signals can be used in lieu of “software code,” and therefore,may be directly integrated into the control logic of mobile device 101,thereby requiring less processing and hence, less power. It iscontemplated, however, that coded instructions may also be utilized. Assuch, these control signals may be utilized by API(s) 119 to facilitatethe remote control and/or tracking services of system 100.

It is noted that control signals generated by, for example, remoteapplication 121 of platform 103 may be transmitted to mobile devices 101via one or more of communication networks 109-115. To preventunauthorized individuals from accessing the remote control and/ortracking services of platform 103, authentication information may berequired. For instance, a username and password procedure may beemployed. According to one embodiment, subscribers may be required toenter a code (e.g., personal identification number (PIN), etc.) beforeaccessing the features and functionality of platform 103. Similarly, toprevent the implementation of unauthorized control signals otherwisereceived at mobile device 101, platform 103 may include anauthentication identifier when transmitting control signals to mobiledevices 101. For instance, control signals may be encrypted, eithersymmetrically or asymmetrically, such that a hash value can be utilizedto authenticate received control signals, as well as ensure that thosecontrol signals have not been impermissibly alerted in transit. As such,control signals may include various identifiers, keys, random numbers,random handshakes, digital signatures, and the like. Further, theseauthenticating schemas may themselves be encrypted or otherwise secured.

According to exemplary embodiments, mobile devices 101 may include oneor more application protocol interfaces (API), such as a set of APIsincluded within, for example, a binary runtime environment for wireless(BREW) platform, for receiving control signals from platform 103 and,thereby, for being remotely activated, controlled, configured,monitored, tracked, etc., by platform 103. It is contemplated, however,that one or more other mobile client applications may be utilized, suchas one or more applications written in one or more programminglanguages, such as C, C++, J2ME, Java, etc. As such, API(s) 119 may beconfigured to, in response to control signals being received from, forinstance, platform 103, enable one or more signals to be captured froman audio interface (e.g., a microphone) or an imaging interface (e.g., acamera) of mobile device 101. These signals may relate to acoustic(s) orimage(s) of an environment surrounding mobile device 101. In otherinstances, API(s) 119 may determine spatial positioning, backup or erasea memory (not shown), configure (or reconfigure) functions, obtain usagelogs, terminate services, etc., of or associated with mobile devices101.

In exemplary embodiments, mobile devices 101 transmit, via one or moreof networks 109-115, the one or more signals captured from an audiointerface and/or an imaging interface of mobile devices 101 to platform103. Other information or signals may also be transmitted by mobiledevices 101 to platform 103, such as spatial positioning information,device usage information, images of memories of mobile devices 101, etc.These signals and/or information may be stored to any suitable storagelocation or memory of (or accessible to) the components and/orfacilities of system 100, such as tracking content repository 123. Inother instances, the signals and/or information may be presented tosubscribers, such as via one or more GUI(s). Exemplary GUIs for remotelycontrolling and tracking a mobile device 101 and presenting signalsand/or information provided by controlled or tracked mobile devices 101to subscribers are described in more detail in accordance with FIGS. 8and 6, respectively.

Still further, remote application 121 may enable subscribers to report astatus of their mobile devices 101 to an administrative agency 127, suchas for reporting a mobile device 101 as lost, misplaced, stolen, etc.Subscribers may generate user profiles including one or more variables,values, parameters, polices, etc., for specifying one or more particularadministrative agencies 127 that are to receive generated reports, suchas one or more police departments within a predetermined vicinity of theenvironment surrounding a tracked and located mobile device 101, amanager of an organization responsible for the mobile device 101, etc.It is noted that generated reports may also include one or more of thecaptured signals and/or information received from mobile device 101. Forinstance, a report may include information tracking the spatialpositioning of mobile device 101 in real-time, such that theadministrative agency 127 (or other authorized individuals or entities)can “chase after” mobile device 101. Such a scenario can be useful whenmobile device 101 is stolen and the authorities (e.g., police) aredispatched to retrieve device 101 from the perpetrator(s).

As seen in FIG. 1, service provider network 111 enables client devices101, 105, and 107 to access the features and functionality of platform103 via one or more of networks 109, 113, and 115. Networks 109-115 maybe any suitable wireline and/or wireless network. For example, telephonynetwork 113 may include a circuit-switched network, such as the publicswitched telephone network (PSTN), an integrated services digitalnetwork (ISDN), a private branch exchange (PBX), or other like network.Wireless network 115 may employ various technologies including, forexample, code division multiple access (CDMA), enhanced data rates forglobal evolution (EDGE), general packet radio service (GPRS), mobile adhoc network (MANET), global system for mobile communications (GSM),Internet protocol multimedia subsystem (IMS), universal mobiletelecommunications system (UMTS), etc., as well as any other suitablewireless medium, e.g., microwave access (WiMAX), wireless fidelity(WiFi), satellite, and the like. Meanwhile, data network 109 may be anylocal area network (LAN), metropolitan area network (MAN), wide areanetwork (WAN), the Internet, or any other suitable packet-switchednetwork, such as a commercially owned, proprietary packet-switchednetwork, such as a proprietary cable or fiber-optic network.

Although depicted as separate entities, networks 109-115 may becompletely or partially contained within one another, or may embody oneor more of the aforementioned infrastructures. For instance, serviceprovider network 111 may embody circuit-switched and/or packet-switchednetworks that include facilities to provide for transport ofcircuit-switched and/or packet-based communications. It is furthercontemplated that networks 109-115 may include components and facilitiesto provide for signaling and/or bearer communications between thevarious components or facilities of system 100. In this manner, networks109-115 may embody or include portions of a signaling system 7 (SS7)network, or other suitable infrastructure to support control andsignaling functions. As such, the conjunction of networks 109-115 may beadapted to facilitate the remote control and tracking services of system100.

According to exemplary embodiments, client devices 101, 105, and 107 mayinclude any customer premise equipment (CPE) capable of sending and/orreceiving information over one or more of networks 109-115. Forinstance, voice terminal 107 may be any suitable plain old telephoneservice (POTS) device, facsimile machine, etc., whereas mobile terminal101 may be any cellular phone, radiophone, satellite phone, smart phone,wireless phone, or any other suitable mobile device, such as a personaldigital assistant (PDA), pocket personal computer, tablet, customizedhardware, etc. Further, computing device 105 may be any suitablecomputing device, such as a VoIP phone, skinny client control protocol(SCCP) phone, session initiation protocol (SIP) phone, IP phone,personal computer, softphone, workstation, terminal, server, etc. Eventhough only a limited number of user devices 101, 105, and 107 areillustrated, it is contemplated that system 100 can support a pluralityof user devices 101, 105, and 107.

As previously mentioned, system 100 may also include user profilesrepository 117 for storing subscriber information, such as billinginformation, contact information, demographic information, locationinformation, mobile station configurations, subscription parameters, andthe like. User profiles repository 117 may also be utilized to storedata relating to authorized users of the remote control and trackingservices of system 100, as well as associated authorization informationcorresponding to those users. Namely, a user of mobile device 101 mayestablish one or more sub-profiles including usernames, passwords,codes, PINs, etc. to further distinguish various override scenarios.While user profiles repository 117 is depicted as an extension ofservice provider network 111, it is contemplated that user profilesrepository 117 can be integrated into, collocated at, or otherwise incommunication with any of the components or facilities of system 100.

In this manner, repositories 117 and 123 may be maintained by a serviceprovider of the remote control and tracking services of system 100 ormay be maintained by any suitable third-party. It is contemplated thatthe physical implementation of repositories 117 and 123 may take on manyforms, including, for example, portions of existing repositories of aservice provider, new repositories of a service provider, third-partyrepositories, and/or shared-repositories. As such, repositories 117 and123 may be configured for communication over system 100 through anysuitable messaging protocol, such as lightweight directory accessprotocol (LDAP), extensible markup language (XML), open databaseconnectivity (ODBC), structured query language (SQL), and the like, aswell as combinations thereof. In those instances when repositories 117and 123 are provided in distributed fashions, information and contentavailable via repositories 117 and 123 may be located utilizing anysuitable querying technique, such as electronic number matching,distributed universal number discovery (DUNDi), uniform resourceidentifiers (URI), etc.

Thus, a subscriber of (or an individual authorized to use) the remotecontrol and tracking services of system 100 may initialize acommunication session at client devices 105 and 107, as well as atanother mobile unit (not shown) to interact with remote application 121so as to remotely control, configure, monitor, track, etc., mobiledevice 101. Furthermore, although the remote control and trackingservices are described with respect to a mobile device 101, it isrecognized that the remote control and tracking services may be appliedto any device capable of providing voice communications, such as clientdevices 105 and 107. In other instance, mobile devices 101 may beintegrated with other devices, individuals, objects, etc., and therebyenable subscribers to remotely control, configure, monitor, and/or trackthese other devices, individuals, objects, etc. While system 100 hasbeen described in accordance with the depicted embodiment of FIG. 1, itis contemplated that system 100 may embody many forms and includemultiple and/or alternative components and facilities.

FIG. 2 is a diagram of a tracking platform capable of providing remotecontrol and tracking services, according to an exemplary embodiment.Tracking platform (or platform) 200 may comprise computing hardware(such as described with respect to FIG. 10), as well as include one ormore components configured to execute the processes described herein forproviding the remote control and tracking services of system 100. In oneimplementation, platform 200 includes communication interface 201,controller (or processor) 203, memory 205, messaging module 207,presence service module 209, reporting module 211, and user interfacemodule 213. Platform 200 may also communicate with one or morerepositories, such as tracking content repository 215 and user profilesrepository 217. Users may access platform 200 (or the features andfunctionality provided thereby) via client devices 101, 105, and 107.While specific reference will be made to this particular implementation,it is also contemplated that platform 200 may embody many forms andinclude multiple and/or alternative components. For example, it iscontemplated that the components of platform 200 may be combined,located in separate structures, or separate locations.

According to one embodiment, platform 200 embodies one or moreapplication servers accessible to client devices 101, 103, and 105 overone or more networks 109-115. Users (or subscribers) can access platform200 to create, customize, and manage one or more user profiles (such asfor the purpose of registering mobile devices 101 with the remotecontrol and tracking services of system 100), as well as for remotelycontrolling and tracking one or more of these registered mobile devices101. As such, platform 200 may provide a user interface, e.g., webportal or other networked application, to permit user to access thefeatures and functionality of platform 200 via client devices 101, 105,and 107. According to certain embodiments, user interface module 213 maybe configured for exchanging information between client devices 101,105, and 107 and a web browser or other network-based application orsystem, such as a voice browser or interactive voice recognition system.

In exemplary embodiments, user interface module 213 may be configured toexecute one or more GUIs that are configured to provide users with oneor more menus of options for creating, customizing, and managing userprofiles, as well as engaging with the other features andfunctionalities of the remote control and tracking services of system100, such as to enable subscribers to remotely determine and monitor thelocation and/or surrounding environment of mobile devices 101 when, forinstance, the users misplace (or otherwise lose) their devices 101.Additionally (or alternatively), platform 200 may enable users toremotely control mobile devices 101 in order to, for example, backup orerase a memory (not shown), capture signals from an interface (e.g.,audio interface, imaging interface, etc.), configure (or reconfigure)functions, obtain usage logs, terminate services, etc., of or associatedwith these devices 101. As previously mentioned, exemplary GUIs aredescribed in more detail in accordance with FIGS. 6 and 8.

In this manner, user interface module 213 (via communication interface201) may be configured to receive requests for remotely controlling,configuring, monitoring, tracking, etc., mobile devices 101. Forexample, a subscriber may access platform 200 via a suitable clientdevice (e.g., computing device 105) to remotely control and/or tracktheir lost or otherwise misplaced mobile device 101. The subscriber maysubmit a corresponding request to track mobile device 101 and, inresponse thereto, user interface module 213 may port the request tomessaging module 207 for generating suitable control signals forremotely controlling and/or tracking mobile device 101.

Accordingly, messaging module 207 is configured to generate one or morecontrol signals based on the request that, when received by mobiledevice 101, are configured to remotely activate one or more applications(e.g., API(s) 119) on mobile device 101. The control signals may furtherbe configured to control an audio interface or an imaging interface ofmobile device 101, such as to remotely capture one or more signals fromthe audio interface or the imaging interface, which provide indiciarelated to an environment surrounding mobile device 101. In this manner,messaging module 207 via, for example, communication interface 201, mayalso be configured to transmit generated control signal(s) to mobiledevice 101, such as over one or more communication networks 109-115 and,in response thereto, configured to receive one or more capturedsignal(s) from mobile device 101 that are related to the environmentsurrounding mobile device 101. As will become more apparent below,messaging module 207, via communication interface 201, may also beconfigured to receive other information from mobile device 101, such asspatial positioning information relating to a location of mobile device101, an image of a memory of mobile device 101, a usage log of mobiledevice 101, etc.

According to exemplary embodiments, messaging module 207 may beconfigured to generate control signals for transmission to mobile device101 utilizing any suitable bearer, such one or more call control setupmessages, short messaging service (SMS) messages, enhanced messagingservice (EMS) messages, multimedia messaging service (MMS) messages,electronic mail, files, or any other suitable bearer, as well as anysuitable combination thereof. In particular implementations, thesebearer mediums may include control signals in various forms, includingattention (AT) commands, menu traversal paths, function codes, voicedata, dual-tone multi-frequency (DTMF) signals, scripts, strings,parameters, object variables, and the like. It is noted that thesecontrol signals can be used in lieu of “software code,” and therefore,may be directly integrated into the control logic of mobile device 101,thereby requiring less processing and hence, less power. It iscontemplated, however, that coded instructions may also be utilized. Itis also contemplated that these control signals and/or bearers may beAPI directed, such as BREW directed.

As seen in FIG. 2, platform 200 may include presence service module 209for receiving and, thereby, tracking real-time spatial positioninginformation from corresponding mobile devices 101. Additionally,presence service module 209 may “poll” mobile devices 101 for spatialpositioning information, as well as capture presence information oravailability of mobile devices 101. An exemplary model for presencedetermination is detailed in Internet Engineering Task Force (IETF)Request for Comment (RFC) 2778, which is incorporated herein byreference in its entirety. According to certain exemplary embodiments,the presence or availability of mobile devices 101 may be utilized todetermine whether control signals may be transmitted to mobile devices101, as well provide subscribers with additional information forretrieving their mobile device 101 or ascertaining the identity of apotential perpetrator.

In this manner, captured signals and/or information received from mobiledevices 101 may be stored to tracking content repository 215 or anyother suitable storage location or memory of (or accessible to) platform200, such as memory 205. This tracking content may also be ported touser interface module 213 for presentation to subscribers via the one ormore GUIs. It is noted that this tracking content may relate to signalscaptured from an audio interface (e.g., a microphone) or an imaginginterface (e.g., a camera) of mobile device 101, spatial positioninginformation relating to a location of mobile device 101, a device usagelog corresponding to use of mobile device 101, an image of a memory ofmobile device 101, etc., as well as any other suitable content that mayfacilitate the retrieval of lost, stolen, or otherwise misplaced mobiledevices 101 or assist in the identification of a potential perpetrator.

According to exemplary embodiments, presenting tracking content to asubscriber enables the subscribers to determine a location of theirdevices 101. As such, user interface module 213 may be configured toconvey the location (or spatial position) of a mobile device 101 to thesubscriber, which may be provided as a short or multimedia message orprovided within an automated or personnel-based voice call. In certainembodiments, the spatial position or location of a mobile device 101 maybe overlaid on a topical depiction (or map) of a cartographic orgeographic area, such that pinpointing the location of mobile device 101can be quickly ascertained. It is also contemplated that user interfacemodule 213 may provide routing directions for directing the subscriberto the location of the lost, misplaced, or stolen device.

Subscribers may also utilize the features and functionalities ofplatform 200 to report a status of their mobile device 101 to anadministrative agency, such as for reporting a mobile device 101 aslost, misplaced, stolen, etc. In this manner, user interface module 213may provide one or more menus, options, tasks, routines, selections,etc., to enable subscribers to submit such requests. A request to reporta mobile device status to one or more administrative agencies 127 may beported to reporting module 211. In exemplary embodiments, reportingmodule 211 is configured to generate, in response to received requests,a report including the mobile device status for transmission to one ormore administrative agencies, such as one or more predefinedadministrative agencies 127 stored to a user profile corresponding tothe subscriber and/or lost, stolen, or otherwise misplaced mobile device101. For instance, a subscriber may generate a user profile includingone or more variables, values, parameters, polices, etc., for specifyingone or more particular administrative agencies 127 that are to receivegenerated reports, such as one or more police departments within apredetermined vicinity of the environment surrounding mobile device 101,a manager of an organization responsible for the mobile device 101, etc.It is noted that generated reports may also include one or more of thecaptured signals and/or information received from mobile device 101. Forinstance, a report may include information tracking the spatialpositioning of mobile device in real-time, such that the administrativeagency 127 (or other authorized individuals or entities) can “chaseafter” mobile device 101. Such a scenario can be useful when mobiledevice 101 is stolen and the authorities (e.g., police) are dispatchedto retrieve device 101 from the perpetrator(s). Thus, reporting module211 via, for instance, communication interface 201, may be configured totransmit generated reports to these administrative agencies 127 over oneor more of networks 109-115.

In order to provide selective access to the features and functionalityof platform 200, platform 200 may also include an authentication module(not illustrated) for authenticating (or authorizing) users to platform200. It is contemplated that the authentication module may operate inconcert with communication interface 201 and/or user interface module213. That is, the authentication module may verify user providedcredential information acquired via communication interface 201 and/oruser interface module 213 against corresponding credential informationstored within a user profile of, for instance, user profiles repository217. By way of example, the credential information may include “log on”information corresponding to a user name, password, coded key, or otherunique identification parameter, such a personal identification number(PIN). In other instances, the credential information may include anyone or combination of a birth date, an account number (e.g., bank,credit card, billing code, etc.), a social security number (SSN), anaddress (e.g., work, home, internet protocol (IP), media access control(MAC), port, etc.), or telephone listing (e.g., work, home, cellular,etc.), as well as any other form of uniquely identifiable datum, e.g.,bearer tag identifier, biometric code, voice print, etc. Subscribers mayprovide this information via client devices 101, 105, and 107, such asby spoken utterances, dual-tone multi-frequency (DTMF) signals,packetized transmission, etc. It is contemplated that unobtrusivesecurity may be provided by positively identifying and screening usersbased on one or more of the aforementioned credentials which may beseamlessly provided when client devices 101, 105, and 107 communicatewith platform 200, such as a unique IP or MAC address. Other unobtrusivemeasures can be made available via voice prints, etc.

Additionally, platform 200 may include one or more controllers (orprocessors) 203 for effectuating the aforementioned features andfunctionality of the remote control and tracking services of system 100,as well as one or more memories 205 for permanent and/or temporarystorage of one or more of the aforementioned variables, parameters,information, signals, etc. In this manner, the features andfunctionalities of remote application 121 may be executed bycontroller(s) 203 and/or memories 205, such as in conjunction with oneor more of the various components of platform 200.

FIG. 3 is a diagram of a mobile device configured to facilitate remotecontrol and tracking services, according to an exemplary embodiment.Mobile device 300 may comprise computing hardware (such as describedwith respect to FIG. 10), as well as include one or more componentsconfigured to execute the processes described herein for facilitatingthe remote tracking services of system 100. In this example, mobiledevice 300 includes application programming interface(s) 301, camera303, communications circuitry 305, and user interface 307. Whilespecific reference will be made hereto, it is contemplated that mobiledevice 300 may embody many forms and include multiple and/or alternativecomponents.

According to exemplary embodiments, user interface 305 may include oneor more displays 309, keypads 311, microphones 313, and/or speakers 315.Display 309 provides a graphical user interface (GUI) that permits auser of mobile device 300 to view dialed digits, call status, menuoptions, and other service information. The GUI may include icons andmenus, as well as other text and symbols. Keypad 309 includes analphanumeric keypad and may represent other input controls, such as oneor more button controls, dials, joysticks, touch panels, etc. The userthus can construct user profiles, enter commands, initializeapplications, input remote addresses, select options from menu systems,and the like. Microphone 311 coverts spoken utterances of a user (orother auditory sounds, e.g., environmental sounds) into electronic audiosignals, whereas speaker 313 converts audio signals into audible sounds.

Communications circuitry 305 may include audio processing circuitry 321,controller 323, location module 325 (such as a GPS receiver) coupled toantenna 327, memory 329, messaging module 331, transceiver 333 coupledto antenna 335, and wireless controller 337 coupled to antenna 339.Memory 329 may represent a hierarchy of memory, which may include bothrandom access memory (RAM) and read-only memory (ROM). Computer programinstructions and corresponding data for operation can be stored innon-volatile memory, such as erasable programmable read-only memory(EPROM), electrically erasable programmable read-only memory (EEPROM),and/or flash memory. Memory 329 may be implemented as one or morediscrete devices, stacked devices, or integrated with controller 323.Memory 329 may store information, such as one or more user profiles, oneor more user defined policies, one or more contact lists, personalinformation, sensitive information, work related information, etc.

Additionally, it is contemplated that mobile device 300 may also includeone or more applications and, thereby, may store (via memory 329) dataassociated with these applications for providing users with browsingfunctions, business functions, calendar functions, communicationfunctions, contact managing functions, data editing (e.g., database,word processing, spreadsheets, etc.) functions, financial functions,gaming functions, imaging functions, messaging (e.g., electronic mail,IM, MMS, SMS, etc.) functions, multimedia functions, service functions,storage functions, synchronization functions, task managing functions,querying functions, and the like. As such, control signals received bymobile device 300 from, for example, platform 103 may be utilized byAPI(s) 301 and/or controller 323 to facilitate remotely configuring,modifying, and/or utilizing one or more features, options, settings,etc., of these applications. It is also contemplated that these (orother) control signals may be utilized by controller 323 to facilitateremotely backing up and/or erasing data associated with theseapplications. In other instances, the control signals may cause mobiledevice 300 to become completely or partially deactivated or otherwiseinoperable.

Accordingly, controller 323 controls the operation of mobile station300, such as in response to commands received from API(s) 301 and/ordata stored to memory 329. Control functions may be implemented in asingle controller or via multiple controllers. Suitable controllers 323may include, for example, both general purpose and special purposecontrollers and digital signal processors. Controller 323 may interfacewith audio processing circuitry 321, which provides basic analog outputsignals to speaker 319 and receives analog audio inputs from microphone313. In exemplary embodiments, controller 323 may be controlled byAPI(s) 301 in order to capture signals from camera 303 or microphone 313in response to control signals received from platform 103. In otherinstances, controller 323 may be controlled by API(s) 301 to causelocation module 325 to determine spatial positioning informationcorresponding to a location of mobile device 300. Still further,controller 323 may be controlled by API(s) 301 to image (e.g., backup)and/or erase memory 329, to configure (or reconfigure) functions ofmobile device 300, to track and generate device usage logs, or toterminate services available to mobile device 300. It is noted thatcaptured signals, device usage logs, memory images, spatial positioninginformation, and the like, may be transmitted to platform 103 viatransceiver 333 and/or wireless controller 337. In this manner, thecaptured signals and/or other forms of information may be presented tousers and stored to one or more networked storage locations, such asuser profiles repository 117, tracking content repository 123, or anyother suitable storage location or memory of (or accessible to) thecomponents and facilities of system 100.

It is noted that real time spatial positioning information may beobtained or determined via location module 325 using, for instance,satellite positioning system technology, such as GPS technology. In thisway, location module 325 can behave as (or substantially similar to) aGPS receiver. Thus, mobile device 300 employs location module 325 tocommunicate with constellation 125 of satellites. These satellites 125transmit very low power interference and jamming resistant signalsreceived by GPS receivers 325 via, for example, antennas 327. At anypoint on Earth, GPS receiver 325 can receive signals from multiplesatellites, such as six to eleven. Specifically, GPS receiver 325 maydetermine three-dimensional geolocation (or spatial positioninginformation) from signals obtained from at least four satellites.Measurements from strategically positioned satellite tracking andmonitoring stations are incorporated into orbital models for eachsatellite to compute precise orbital or clock data. Accordingly, GPSsignals may be transmitted over two spread spectrum microwave carriersignals that can be shared by GPS satellites 125. Thus, if mobile device300 is able to identify signals from at least four satellites 125,receivers 325 may decode the ephemeris and clock data, determine thepseudo range for each satellite 125 and, thereby, compute the spatialpositioning of a receiving antenna 327. With GPS technology, mobiledevice 300 can determine its spatial position with great accuracy andconvenience. It is contemplated, however, that location module 325 mayutilize one or more other location determination technologies, such asadvanced forward link triangulation (AFLT), angle of arrival (AOA),assisted GPS (A-GPS), cell identification (cell ID), observed timedifference of arrival (OTDOA), enhanced observed time of difference(E-OTD), enhanced forward link trilateration (EFLT), network multipathanalysis, and the like.

Mobile device 300 also includes messaging module 331 that is configuredto receive, transmit, and/or process messages (e.g., EMS messages, SMSmessages, MMS messages, IM messages, electronic mail messages, and/orany other suitable message) received from (or transmitted to) platform103 or any other suitable component or facility of system 100. Aspreviously mentioned, platform 103 may transmit control singles tomobile device 300 in the form of one or more API 301 directed messages,e.g., one or more BREW directed SMS messages. As such, messaging module331 may be configured to identify such messages, as well as activateAPI(s) 301, in response thereto. Furthermore, messaging module 331 maybe further configured to parse control signals from these messages and,thereby, port parsed control signals to corresponding components ofmobile device 300, such as API(s) 301, controller 323, location module325, memory 329, transceiver 333, wireless controller 337, etc., forimplementation.

According to exemplary embodiments, API(s) 301 (once activated) isconfigured to effectuate the implementation of the control signalsreceived from platform 103, e.g., from remote application 121. It isnoted that the control signals are utilized by API(s) 301 to, forinstance, remotely control, configure, monitor, track, and/or capturesignals from (or related to) camera 103, communications circuitry 305,and/or user interface 307. In this manner, visual and/or acousticindicia pertaining to an environment surrounding mobile device 300 maycaptured by API(s) 301 controlling camera 303 and microphone 313. Othercontrol signals to cause mobile device 300 to determine spatialpositioning information, to image and/or erase memory 329, to configure(or reconfigure) functions, to track and generate device usage logs, orto terminate services, may also be carried out via API(s) 301. As such,one or more signals captured from camera 303 or microphone 313, ordevice usage logs, memory images, spatial positioning information, etc.,may be transmitted to platform 103 via transceiver 333 and/or wirelesscontroller 337, in response to corresponding control signals provided totransceiver 333 and/or wireless controller 337 by API(s) 301. Thus,captured signals and/or one or more other forms of information providedto platform 103 may be presented to users and/or stored to one or moreof user profiles repository 117 and tracking content repository 123, orany other suitable storage location or memory of (or accessible to) thecomponents and facilities of system 100.

It is also noted that mobile device 300 can be equipped with wirelesscontroller 337 to communicate with a wireless headset (not shown) orother wireless network. The headset can employ any number of standardradio technologies to communicate with wireless controller 337; forexample, the headset can be BLUETOOTH enabled. It is contemplated thatother equivalent short range radio technology and protocols can beutilized. While mobile device 300 has been described in accordance withthe depicted embodiment of FIG. 3, it is contemplated that mobile device300 may embody many forms and include multiple and/or alternativecomponents.

FIG. 4 is a flowchart of a process for subscribing a user to remotecontrol and tracking services, according to an exemplary embodiment. Forillustrative purposes, the process is described with respect to FIGS. 1and 2. It is noted that the steps of the process may be performed in anysuitable order, as well as combined or separated in any suitable manner.At step 401, platform 200 subscribes a user associated with one or moremobile devices (e.g., mobile device 101) to the remote control andtracking services of system 100. According to one embodiment, the usermay subscribe utilizing any suitable client device capable of processingand transmitting information over one or more of networks 109-115, suchas computing device 105. Namely, the user may interact with an inputinterface (e.g., a keyboard, interactive voice response (IVR) interface,etc.) of, for example, computing device 105 to activate softwareresident on device 105, such as a GUI or other networked applicationthat interfaces with (or is implemented by) platform 200. Alternatively,the user may interact with a voice portal (not shown) interfacing with(or implemented by) platform 200, wherein speech synthesis and voicerecognition techniques are utilized to prompt the user for variousinformation and to reduce spoken utterances of the user and/or othersignals (e.g., dual tone multi-frequency signals) associated with theuser to one or more corresponding inputs. As such, the user can registeras a new subscriber of the remote control and tracking services and mayobtain sufficient authentication information for establishing futuresessions with platform 200.

According to certain embodiments, registration procedures may prompt theuser to identify mobile devices 101 and/or other client devices, e.g.,client devices 105 and 107 that the user may wish to remotely controland/or track when, for instance, such devices become misplaced, lost, oreven stolen. In this manner, the user may uniquely identify thesedevices 101, 105, and 107 by entering appropriate device information (oridentifiers), such as one or more device types, serial numbers,registration numbers, MAC addresses, directory addresses, communicationslinks, etc., corresponding to devices 101, 105, and 107. In certainexemplary embodiments, platform 200 may obtain correspondingconfiguration and/or interfacing information relating to these devicesfrom, for example, one or more manufacturers or other third-partysuppliers over, for instance, data network 109. It is noted that thisconfiguration and/or interfacing information may be utilized by platform200 to facilitate the remote control and tracking services of system100. Furthermore, the configuration and/or interfacing information maybe stored to any suitable storage location or memory of (or accessibleto) system 100, such as user profiles repository 117.

Once registered (or as part of the registration process), platform 200enables the user, per step 403, to generate and/or customize a userprofile. The user profile may include addressing information (e.g.,directory number, electronic serial number, international mobileequipment identifier, machine access control address, mobile directorynumber, mobile equipment identity, mobile identification number,internet protocol address, port address, and/or any other suitableaddress) corresponding to identified client devices 101, 105, and 107that the user desires to register with the remote control and trackingservices of system 100, as well as include other personal and/or servicerelated information, parameters, polices, variables, etc., such asconfiguration and/or interfacing information, predeterminedadministrative agencies, and the like. At step 405, platform 200 storesthe user to a list of subscribers to the remote control and trackingservices of system 100, as well as stores the generated user profile,authentication information, device identifies, etc., to, for example,user profiles repository 117. It is noted that platform 200 mayadditionally (or alternatively) store or synchronize this user profileinformation to any suitable storage location or memory of (or accessibleto) platform 200. Further, it is contemplated that users may directlyinteract with one or more of these storage facilities or memories, suchas user profiles repository 117.

FIGS. 5A and 5B are flowcharts of processes for remotely tracking amobile device, according to exemplary embodiments. For illustrativepurposes, these processes are described with reference to FIGS. 1-3. Itis also noted that the process involves, for example, mobile device 300becoming misplaced, lost, or stolen. Further, the steps of the processesmay be performed in any suitable order, as well as combined or separatedin any suitable manner. In particular, FIG. 5A is utilized to describethese processes from the perspective of platform 200, whereas FIG. 5B isutilized to describe these process from the perspective of mobile device300.

At step 501, platform 200 receives a request to track mobile device 300,which may be lost, stolen, or otherwise misplaced. That is, a subscribervia, for example, computing device 105 establishes a communicationsession with platform 200, such as by “logging on” to a networkedapplication (e.g., remote application 121) provided by, for instance,user interface module 213. It is noted that before gaining access, thesubscriber may be required to provide credential information, such as ausername and password combination. Once “logged on,” user interfacemodule 213 may prompt the user with one or more GUIs menus, options,selections, etc., enabling the subscriber to formulate the request, aswell as input an address (e.g., telephone number, machine identifier,media access control (MAC) address, internet protocol (IP) address,etc.) of mobile device 300 that the user wants to remotely track.

In step 503, user interface module 213 ports the request to, forinstance, messaging module 207 to generate one or more control signalsto remotely activate an application (e.g., API(s) 301, on mobile device300 for controlling an audio interface (e.g., microphone 313) or animaging interface (e.g., camera 303) of mobile device 300. As previouslymentioned, messaging module 207 may be configured to generate controlsignals for transmission to mobile device 300 utilizing via variousbearers, such as in the form of one or more call control setup messages,short messaging service (SMS) messages, enhanced messaging service (EMS)messages, multimedia messaging service (MMS) messages, electronic mail,files, or any other suitable bearer, as well as any suitable combinationthereof. These messages may further be directed to API(s) 301, such asone or more BREW directed SMS messages. Thus, at step 505, messagingmodule 207 via, for example, communication interface 201, transmits theone or more generated control signals (e.g., the one or more BREWdirected SMS messages) to mobile device 300 over one or more of networks109-115 and, in particular, via wireless network 115.

At step 507, communication interface 201 receives one or more signalscaptured from the audio interface or the imaging interface of mobiledevice 300 that, in exemplary embodiments, correspond to acoustic and/orvisual indicia of an environment surrounding mobile device 300. Further,per step 509, communication interface 201 may also receive spatialpositioning information corresponding to a location of mobile device300. It is noted that the captured signals and/or spatial positioninginformation may be stored to tracking content repository 123 or anyother suitable storage location of (or accessible to) system 100, suchas user profiles repository 117. Accordingly, at step 511, userinterface module 213 presents the captured signals (or informationcorresponding to these signal(s)) and/or the spatial positioninginformation via the networked interface, e.g., via one or more GUIsimplemented by user interface module 213.

Referring now to FIG. 5B, mobile device 300 via, for instance,transceiver 333 receives one or more control signals configured toremotely activate an application (e.g., one or more of API(s) 301)configured to control an audio interface (e.g., microphone 313) or animaging interface (e.g., camera 303) of mobile device 300. In exemplaryembodiments, the control signals may be couched in one or more callcontrol setup messages, short messaging service (SMS) messages, enhancedmessaging service (EMS) messages, multimedia messaging service (MMS)messages, electronic mail, files, or any other suitable bearer, as wellas any suitable combination thereof. Accordingly, transceiver 333 mayport received messages to messaging module 331 for identifying themessages as remote control signals, as well as parsing received messagesfor corresponding control signals. In this manner, messaging module 331ports the control signals to API(s) 301, which remotely activate API(s)301 for executing one or more applications to capture one or moresignals from the audio interface or the imaging interface of mobiledevice 300, per step 553. At step 555, API(s) 301 control the audiointerface or the imaging interface to capture one or more signals that,in exemplary embodiments, pertain to acoustic and/or visual indicia ofan environment surrounding mobile device 300. According to certainembodiments, API(s) 301 may also provide suitable control signals tolocation module 325 to determine, per step 557, spatial positioninginformation corresponding to a location of mobile device 300. Thus, instep 559, mobile device 300 via, for instance, transceiver 333,transmits the captured signals and/or the spatial positioninginformation to platform 200, such as over one or more of networks109-115. It is noted that this spatial positioning information and/orthe captured signals, when presented to a subscriber, will facilitatethe subscriber's efforts in locating and recovering mobile device 300 oridentifying a potential perpetrator who may have stolen mobile device300 from the subscriber.

FIG. 6 is a graphical user interface for remotely tracking a mobiledevice, according to an exemplary embodiment. In this example, it isassumed that GUI 600 is provided to a subscriber of the remote controland tracking services of system 100 by platform 200 via, for instance,user interface module 213. It is also assumed that the subscriber hasregistered a plurality of devices, such as a plurality of mobile devices101, with the remote control and tracking services of system 100. Hence,GUI 600 includes a plurality of “tabs” (or interactive interfaceelements) 601 a-601 n corresponding to registered devices of (orassociated with) the subscriber. A plurality of other tabs, e.g.,“CONTROLLING” tab 603, “TRACKING” tab 605, and “USER PROFILE” tab 607provides the subscriber with various “main” remote controlling andtracking features or functionalities of platform 200. For instance, tab603 enables the subscriber to remotely control devices associated withthe user, such as for backing up or erasing a memory, configuring (orreconfiguring) functions, terminating services, etc., of or associatedwith registered devices. Tab 605 enables subscribers to capture signalsfrom an interface (e.g., audio interface, imaging interface, etc.) ofregistered devices, as well as obtain spatial positioning informationcorresponding to a location of registered devices. Tab 607 enablessubscribers to modify corresponding user profile information, such asregister new devices to the remote control and tracking services ofsystem 100, update personal information, and the like.

Accordingly, selection of (or any other suitable interaction with) tab605 toggles region 609 to an “active” tracking region 609, providingtracking content associated with a particular device. For instance,selection of a particular one of tabs 601 a-601 n toggles “active”tracking region 609 between tracking “DEVICE ‘1,’” DEVICE ‘2,’” . . .“DEVICE ‘N.’” That is, selection of, for example, tab 601 a toggles“active” tracking region 609 to present tracking content correspondingto “DEVICE ‘1.’” It may also be the case that interacting with trackingtab 605 causes a feature (or function) of region 611 to be populatedwith one or more “available” tracking features region 611 providing oneor more available remote control and/or tracking features to thesubscriber, such as a “LOCATE DEVICE” feature 613, a “RECORDAUDIO”feature 615, a “RECORD VIDEO” feature 617, a “REPORT” feature 619,a “USAGE LOG” feature 621, etc. In other embodiments, features region611 may include a navigation tree, an expandable table of contents, orfor example FlashMedia presentation of selectable entries, as well asother equivalent listings, menus, options, etc. The content ofrespective regions (e.g., regions 609 and 611) may be dynamicallyupdated based on one or more selections of features 613-621.

Accordingly, selection of feature 613 provides spatial positioninginformation (e.g., a “current” location) of the device being tracked,which in this example is “DEVICE ‘1.’” As such, a “‘CURRENT’ LOCATION”region 623 may be provided for presenting the subscriber with variousforms of spatial positioning information, such as a street address,latitude, longitude, elevation, etc., as well combinations thereof.According to particular embodiments, a “MAPPING” region 625 may beprovided that overlays the spatial positioning information on, forinstance, a topological depiction of a geographic area surrounding thelocation of the device, which may also be appended with variouscartographic features, such as buildings, landmarks, roadways, signs,and the like. In certain embodiments, the overlay may be apoint-of-interest (POI) marker, such that the subscriber may obtaindirections to the location of the device via interaction with the POImarker.

Selection of feature 615 enables the subscriber to record audio (oracoustics) captured from an audio interface (e.g., microphone 313) ofmobile device 300. This acoustic information may be presented to theuser via suitable transducers of a client device (e.g., computing device105) interfacing with GUI 600. In a similar fashion, selection offeature 617 enables the subscriber to record video captured from, forinstance, an imaging interface (e.g., camera 303) of mobile device 300.Accordingly, an “IMAGING” region 627 may be provide for displaying thecapture video to the subscriber. Further, interaction with, forinstance, a “CAPTURE IMAGE” button 629 allows the subscriber to “take”still images of visual indicia captured via the imaging interface ofmobile device 300.

According to particular embodiments, selection of feature 621 enablesthe subscriber to obtain device usage information (e.g., statistics,summary, descriptions, etc.) pertaining to the use of various features,applications, services, etc., of (or available to) a device beingtracked. Accordingly, a “USAGE LOG” region 631 may be provided todisplay usage information to the subscriber. Moreover, selection offeature 619, allows the subscriber to report a status and/or trackinginformation of the device being actively tracked to an administrativeagency.

Navigational elements/fields, e.g., scrollbars 633 and 635, may beprovided and configured to indicate the existence of additionalinformation, entries, fields, etc., not displayed, but navigablyavailable, as well as facilitate interface usability. Accordingly, thesubscriber may browse to additional information, entries, fields, etc.,via, for instance, an input interface of a suitable client device (e.g.,computing device 105), e.g., a cursor control. One or more fixed focusstates (e.g., borders 637, 639, 641, 643, and 645) and/or distinctivemagnification features, e.g., color, brightness, bolding, font type,text size, etc., may be used to convey the device being “currently”tracked, as well as those remote control and/or tracking features being“currently” employed to remotely control and/or track the particulardevice.

According to additional exemplary embodiments, GUI 600 may includevarious other regions, such as a user name region 647 and a passwordregion 649 for enabling subscribers to “log on” and obtain access to thefeatures and functionalities of GUI 600 and/or platform 200. Inalternative embodiments, regions 647 and 649 may be configured tocorrespond to other associated authentication information. It is notedthat a “WELCOME, USERNAME” message may be presented to authenticatedsubscribers once sufficient authentication (or authorization)information is input to regions 647 and/or 649. Still further, GUI 600may include a service provider logo region 651 to illustrate (orotherwise present) the subscriber with a logo of the service provider ofthe remote control and tracking services of system 100, as well asinclude other suitable (or equivalent) regions, such as an advertisementregion (not shown), etc.

FIGS. 7A and 7B are flowcharts of processes for remotely controlling orconfiguring a mobile device, according to exemplary embodiments. Forillustrative purposes, the process is described with reference to FIGS.1-3. It is also noted that the process involves, for example, mobiledevice 300 becoming misplaced, lost, or stolen. In particular, FIG. 7Ais utilized to describe these processes from the perspective of platform200, whereas FIG. 7B is utilized to describe these process from theperspective of mobile device 300.

At step 701, a subscriber (e.g., owner) of mobile device 300 accessesplatform 200 via, for instance, computing device 105 in order toremotely control or configure mobile device 300, such as for imagingand/or erasing memory 329, configuring (or reconfiguring) one or morefunctions associated with applications or settings of mobile device 300,obtaining usage logs pertaining to the use of mobile device 300, orterminating services, etc., of or associated with mobile device 300.That is, a subscriber via, for example, computing device 105 establishesa communication session with platform 200, such as by “logging on” to anetworked application (e.g., remote application 121) provided by, forinstance, user interface module 213, to submit a request to remotelycontrol or configured mobile device 300. It is noted that before gainingaccess, the subscriber may be required to provide credentialinformation, such as a username and password combination. Once “loggedon,” user interface module 213 may prompt the user with one or more GUIsmenus, options, selections, etc., enabling the subscriber to formulatethe request, as well as input an address (e.g., telephone number,machine identifier, media access control (MAC) address, internetprotocol (IP) address, etc.) of mobile device 300 that the user wants toremotely control and/or configure. It is noted that an exemplary GUI forremotely controlling and/or configured mobile device 300 is described inmore detail in accordance with FIG. 8.

In step 703, user interface module 213 ports the request to, forinstance, messaging module 207 to generate one or more control signalsto remotely activate an application (e.g., API(s) 301, on mobile device300 for imaging and/or erasing memory 329, configuring (orreconfiguring) one or more functions associated with applications orsettings of mobile device 300, obtaining usage logs pertaining to theuse of mobile device 300, or terminating services, etc., of orassociated with mobile device 300. As previously mentioned, messagingmodule 207 may be configured to generate control signals fortransmission to mobile device 300 utilizing via various bearers, such asin the form of one or more call control setup messages, short messagingservice (SMS) messages, enhanced messaging service (EMS) messages,multimedia messaging service (MMS) messages, electronic mail, files, orany other suitable bearer, as well as any suitable combination thereof.These messages may further be directed to API(s) 301, such as one ormore BREW directed SMS messages. Thus, at step 705, messaging module 207via, for example, communication interface 201, transmits the one or moregenerated control signals (e.g., the one or more BREW directed SMSmessages) to mobile device 300 over one or more of networks 109-115 and,in particular, via wireless network 115. Even though not illustrated,when the user employs the process of FIG. 7A to obtain usage loginformation, image memory 329, etc., corresponding information may bereceived by communication interface 201, in response to, transmittingthe control signals to mobile device 300, such as in the process of FIG.5A.

Referring now to FIG. 7B, mobile device 300 via, for instance,transceiver 333 receives one or more control signals configured toremotely activate an application (e.g., one or more of API(s) 301)configured to remotely control or configure mobile device 300, such asfor imaging and/or erasing memory 329, configuring (or reconfiguring)one or more functions associated with applications or settings of mobiledevice 300, obtaining usage logs pertaining to the use of mobile device300, or terminating services, etc., of or associated with mobile device300. In exemplary embodiments, the control signals may be couched in oneor more call control setup messages, short messaging service (SMS)messages, enhanced messaging service (EMS) messages, multimediamessaging service (MMS) messages, electronic mail, files, or any othersuitable bearer, as well as any suitable combination thereof.Accordingly, transceiver 333 may port received messages to messagingmodule 331 for identifying the messages as remote control signals, aswell as parsing received messages for corresponding control signals. Inthis manner, messaging module 331 will port parsed control signals toAPI(s) 301, which remotely activate API(s) 301 for executing, in step753, one or more applications to image and/or erase memory 329,configure (or reconfigure) one or more functions associated withapplications or settings of mobile device 300, obtain usage logspertaining to the use of mobile device 300, or terminate services, etc.,of or associated with mobile device 300. At step 755, API(s) 301 controlcorresponding components of mobile device 300, such as memory 329,location module 325, transceiver 333, etc., to carry out the commands,instructions, processes, etc., delineated within the received controlsignals to control or configure mobile device 300. Even though notillustrated, mobile device is remotely controlled to obtain usage loginformation, image memory 329, etc., corresponding information may betransmitted to platform 200 via transceiver 333, such as in the processof FIG. 5B.

FIG. 8 is a graphical user interface for remotely controlling orconfiguring a mobile device, according to an exemplary embodiment. Inthis example, GUI 800 is provided to a subscriber of the remote controland tracking services of system 100 by platform 200 via, for instance,user interface module 213. It is assumed that the subscriber haspreviously registered one or more devices, e.g., devices 101, with theremote control and tracking services of system 100. Hence, GUI 800, likeGUI 600, includes a plurality of “tabs” (or interactive interfaceelements) 801 a-801 n corresponding to registered devices of (orassociated with) the subscriber. Further, main feature tabs, e.g.,“CONTROLLING” tab 803, “TRACKING” tab 805, and “USER PROFILE” tab 807are provided for accessing the “main” remote controlling and trackingfeatures or functionalities of platform 200. Tabs 803-807 correspond totabs 603-607 and, therefore, are not explained in any further detail.

Accordingly, selection of (or any other suitable interaction with)controlling tab 803 toggles region 809 to an “active” controlling region809, providing a control feature or function associated with aparticular device. For instance, selection of (or any other suitableinteraction with) a particular one of tabs 801 a-801 n toggles “active”control region 809 between controlling “DEVICE ‘1,’” DEVICE ‘2,’” . . .“DEVICE ‘N.’” That is, selection of, for example, tab 801 a toggles“active” controlling region 809 to present a control feature or functioncapable of being configured for “DEVICE ‘1.’” It may also be the casethat interacting with controlling tab 803 causes a features (orfunctions) region 811 to be populated with one or more “available”control features region 611 providing one or more available remotecontrol and/or tracking features to the subscriber, such as a “BACKUPMEMORY” feature 813, a “CLEAR MEMORY” feature 815, a “CONFIGURE” feature817, a “DEACTIVATE” feature 819, etc. In other embodiments, featuresregion 811 may include a navigation tree, an expandable table ofcontents, or for example FlashMedia presentation of selectable entries,as well as other equivalent listings, menus, options, etc. The contentof respective regions (e.g., regions 809 and 811) may be dynamicallyupdated based on one or more selections of features 813-819.

Accordingly, selection of feature 813 enables the subscriber to image orback up one or more memories (e.g., memory 329) of mobile device 300,whereas selection of feature 815 allows the subscriber to clear the oneor more memories, such as to purge the device of sensitive or otherwisepersonal information. Interaction with feature 817 enables thesubscriber to configure one or more features or functions of theactively controlled device, such as configuring a ringtone, operatingstate, display setting, etc., of mobile device 300. Furthermore,selection of feature 819 enables the user to “lock” the device beingremotely controlled until an appropriate “unlock” code (or signal) isinput (or transmitted) to the device. In other instances, feature 819may permanently terminate usage of the device being controlled, such asan “autodestruct” feature or a service termination feature.

Similarly to GUI 600, GUI 800 provides navigational elements/fields,e.g., scrollbars 821 and 823, to indicate the existence of additionalinformation, entries, fields, etc., not displayed, but navigablyavailable, as well as facilitate interface usability. Accordingly, thesubscriber may browse to additional information, entries, fields, etc.,via, for instance, an input interface of a suitable client device (e.g.,computing device 105), e.g., a cursor control. One or more fixed focusstates (e.g., borders 825, 827, and 829) and/or distinctivemagnification features, e.g., color, brightness, bolding, font type,text size, etc., may be used to convey the device being “currently”controlled, as well as those remote control and/or tracking featuresbeing “currently” employed to remotely control and/or track theparticular device.

As seen in FIG. 8, feature 815 has been selected, which is denoted byfixed focus state 829. Accordingly, controlling region 809 provides oneor more menus, options, instructions, buttons, etc., for clearing (orotherwise erasing) a memory of the device being currently controlled.For instance, region 809 provides an instruction region 831 informingthe subscriber that once the memory of the device is erased, theinformation will no longer be available. As such, interaction withinteractive element 833 carries out the erasing function and, thereby,purges the device being controlled of all personal and/or sensitiveinformation, whereas interaction with interactive element 835 cancelsthe clear memory feature. Similar instruction regions, interactiveelements, input fields, etc., may be provided for features 813, 817, and819.

Moreover, like GUI 600, GUI 800 also includes various regions, such as auser name region 837 and a password region 839 for enabling subscribersto “log on” and obtain access to the features and functionalities of GUI800 and/or platform 200. In alternative embodiments, regions 837 and 839may be configured to correspond to other associated authenticationinformation. It is noted that a “WELCOME, USERNAME” message may bepresented to authenticated subscribers once sufficient authentication(or authorization) information is input to regions 837 and/or 839. Stillfurther, GUI 800 may include a service provider logo region 841 toillustrate (or otherwise present) the subscriber with a logo of theservice provider of the remote control and tracking services of system100, as well as include other suitable (or equivalent) regions, such asan advertisement region (not shown), etc.

FIG. 9 is a flowchart of a process for providing tracking informationrelated to a mobile device to an administrative agency, according to anexemplary embodiment. For illustrative purposes, the process isdescribed with reference to FIGS. 1, 2, and 6. In this example, it isassumed that mobile device 300, associated with a subscriber, has beenstolen and that the user wants to report the device as stolen and/orprovide tracking information to an administrative agency, such as alocal police department, in order to facilitate the recovery of thedevice and apprehending potential perpetrators. Further, is noted thatthe steps of the process may be performed in any suitable order, as wellas combined or separated in any suitable manner.

At step 901, user interface module 213 of tracking platform 200 receivesa request to report information corresponding to mobile device to anadministrative agency, e.g., report that mobile device 300 is stolen andprovide the administrative agency with related tracking information (orcontent), such as acoustics, visuals, and spatial positioninginformation corresponding to an environment surrounding mobile device300. For instance, the user may have discovered that their mobile device300 was stolen, accessed tracking platform 200 via, for instance,computing device 105, and interacted with one or more of tabs 601-607and/or 613-621 of GUI 600, which enables the user to remotely controland track mobile device 300, as well as request a report be transmittedto a particular administrative agency, e.g., local police department,based on information received from the device. For example, the user mayselect “REPORT” feature 619 for providing a report to the administrativeagency.

In this manner, user interface module 213 may port the request to, forinstance, reporting module 211 so that reporting module 211 cangenerate, per step 903, a report based on the request and one or morecaptured signals and/or information (e.g., spatial positioninginformation, usage log information, acoustics, visuals, etc.) receivedfrom mobile device 300, such as in accordance with the process of FIGS.5A and/or 7A. According to various exemplary embodiments, the report mayprovide the location (or spatial position) of mobile device 300, as wellas provide a depiction corresponding to a “current” location of device300, e.g., provide a map with a point of interest corresponding to thespatial position of the device within a geographic region. The reportmay also provide one or more images, usage log information, textualdescriptions, etc., of an environment surrounding mobile device 300.According to certain embodiments, the report may be generated to include(or be accompanied by) video and/or audio captured via an audiointerface or imaging interface of device 300, such as audio captured viamicrophone 313 and video captured via camera 301 of mobile device 300.As such, the information provided in the report may pertain to thelocation of the stolen device, the surrounding environment of the stolendevice, and potentially a perpetrator making use of or otherwisepossessing the stolen device. Thus, per step 905, reporting module 211via, for instance, communication interface 201 transmits the generatedreport to the administrative agency, which may be selected by reportingmodule 211 based on information retrieved from user profiles repository117 or one or more commands input to user interface module 213 by thesubscriber. It is also noted that reporting module 211 may provide thesubscriber with a copy (or instance) of the report, as well. In thisway, the remote control and tracking services of system 100 enablesusers to seamlessly report to an administrative agency when, forinstance, their mobile devices 101 become misplaced, lost, or evenstolen, as well as provide administrative agencies (and/or subscribers)with various information, attributes, etc., related to the devices 101,such as the location and/or environment surrounding the device thatfacilitates the recovery of the devices 101 and/or apprehend potentialperpetrators.

The processes described herein for providing remote control and trackingservices for mobile devices may be implemented via software, hardware(e.g., general processor, Digital Signal Processing (DSP) chip, anApplication Specific Integrated Circuit (ASIC), Field Programmable GateArrays (FPGAs), etc.), firmware or a combination thereof. Such exemplaryhardware for performing the described functions is detailed below.

FIG. 10 illustrates computing hardware (e.g., computer system) 1000 uponwhich exemplary embodiments can be implemented. The computer system 1000includes a bus 1001 or other communication mechanism for communicatinginformation and a processor 1003 coupled to the bus 1001 for processinginformation. The computer system 1000 also includes main memory 1005,such as a random access memory (RAM) or other dynamic storage device,coupled to the bus 1001 for storing information and instructions to beexecuted by the processor 1003. Main memory 1005 can also be used forstoring temporary variables or other intermediate information duringexecution of instructions by the processor 1003. The computer system1000 may further include a read only memory (ROM) 1007 or other staticstorage device coupled to the bus 1001 for storing static informationand instructions for the processor 1003. A storage device 1009, such asa magnetic disk or optical disk, is coupled to the bus 1001 forpersistently storing information and instructions.

The computer system 1000 may be coupled via the bus 1001 to a display1011, such as a cathode ray tube (CRT), liquid crystal display, activematrix display, or plasma display, for displaying information to acomputer user. An input device 1013, such as a keyboard includingalphanumeric and other keys, is coupled to the bus 1001 forcommunicating information and command selections to the processor 1003.Another type of user input device is a cursor control 1015, such as amouse, a trackball, or cursor direction keys, for communicatingdirection information and command selections to the processor 1003 andfor controlling cursor movement on the display 1011.

According to an exemplary embodiment, the processes described herein areperformed by the computer system 1000, in response to the processor 1003executing an arrangement of instructions contained in main memory 1005.Such instructions can be read into main memory 1005 from anothercomputer-readable medium, such as the storage device 1009. Execution ofthe arrangement of instructions contained in main memory 1005 causes theprocessor 1003 to perform the process steps described herein. One ormore processors in a multi-processing arrangement may also be employedto execute the instructions contained in main memory 1005. Inalternative embodiments, hard-wired circuitry may be used in place of orin combination with software instructions to implement exemplaryembodiments. Thus, exemplary embodiments are not limited to any specificcombination of hardware circuitry and software.

The computer system 1000 also includes a communication interface 1017coupled to bus 1001. The communication interface 1017 provides a two-waydata communication coupling to a network link 1019 connected to a localnetwork 1021. For example, the communication interface 1017 may be adigital subscriber line (DSL) card or modem, an integrated servicesdigital network (ISDN) card, a cable modem, a telephone modem, or anyother communication interface to provide a data communication connectionto a corresponding type of communication line. As another example,communication interface 1017 may be a local area network (LAN) card(e.g. for Ethernet™ or an Asynchronous Transfer Model (ATM) network) toprovide a data communication connection to a compatible LAN. Wirelesslinks can also be implemented. In any such implementation, communicationinterface 1017 sends and receives electrical, electromagnetic, oroptical signals that carry digital data streams representing varioustypes of information. Further, the communication interface 1017 caninclude peripheral interface devices, such as a Universal Serial Bus(USB) interface, a PCMCIA (Personal Computer Memory Card InternationalAssociation) interface, etc. Although a single communication interface1017 is depicted in FIG. 10, multiple communication interfaces can alsobe employed.

The network link 1019 typically provides data communication through oneor more networks to other data devices. For example, the network link1019 may provide a connection through local network 1021 to a hostcomputer 1023, which has connectivity to a network 1025 (e.g. a widearea network (WAN) or the global packet data communication network nowcommonly referred to as the “Internet”) or to data equipment operated bya service provider. The local network 1021 and the network 1025 both useelectrical, electromagnetic, or optical signals to convey informationand instructions. The signals through the various networks and thesignals on the network link 1019 and through the communication interface1017, which communicate digital data with the computer system 1000, areexemplary forms of carrier waves bearing the information andinstructions.

The computer system 1000 can send messages and receive data, includingprogram code, through the network(s), the network link 1019, and thecommunication interface 1017. In the Internet example, a server (notshown) might transmit requested code belonging to an application programfor implementing an exemplary embodiment through the network 1025, thelocal network 1021 and the communication interface 1017. The processor1003 may execute the transmitted code while being received and/or storethe code in the storage device 1009, or other non-volatile storage forlater execution. In this manner, the computer system 1000 may obtainapplication code in the form of a carrier wave.

The term “computer-readable medium” as used herein refers to any mediumthat participates in providing instructions to the processor 1003 forexecution. Such a medium may take many forms, including but not limitedto non-volatile media, volatile media, and transmission media.Non-volatile media include, for example, optical or magnetic disks, suchas the storage device 1009. Volatile media include dynamic memory, suchas main memory 1005. Transmission media include coaxial cables, copperwire and fiber optics, including the wires that comprise the bus 1001.Transmission media can also take the form of acoustic, optical, orelectromagnetic waves, such as those generated during radio frequency(RF) and infrared (IR) data communications. Common forms ofcomputer-readable media include, for example, a floppy disk, a flexibledisk, hard disk, magnetic tape, any other magnetic medium, a CD-ROM,CDRW, DVD, any other optical medium, punch cards, paper tape, opticalmark sheets, any other physical medium with patterns of holes or otheroptically recognizable indicia, a RAM, a PROM, and EPROM, a FLASH-EPROM,any other memory chip or cartridge, a carrier wave, or any other mediumfrom which a computer can read.

Various forms of computer-readable media may be involved in providinginstructions to a processor for execution. For example, the instructionsfor carrying out at least part of the exemplary embodiments mayinitially be borne on a magnetic disk of a remote computer. In such ascenario, the remote computer loads the instructions into main memoryand sends the instructions over a telephone line using a modem. A modemof a local computer system receives the data on the telephone line anduses an infrared transmitter to convert the data to an infrared signaland transmit the infrared signal to a portable computing device, such asa personal digital assistant (PDA) or a laptop. An infrared detector onthe portable computing device receives the information and instructionsborne by the infrared signal and places the data on a bus. The busconveys the data to main memory, from which a processor retrieves andexecutes the instructions. The instructions received by main memory canoptionally be stored on storage device either before or after executionby processor.

While certain exemplary embodiments and implementations have beendescribed herein, other embodiments and modifications will be apparentfrom this description. Accordingly, the invention is not limited to suchembodiments, but rather to the broader scope of the presented claims andvarious obvious modifications and equivalent arrangements.

1. A method comprising: receiving a request to track a mobile device;and generating, in response to the request, a control signal to remotelyactivate an application on the mobile device for controlling an audiointerface or an imaging interface of the mobile device to capture asignal from the audio interface or the imaging interface.
 2. A methodaccording to claim 1, further comprising: transmitting the controlsignal to the mobile device over a wireless network as part of a shortmessaging service message.
 3. A method according to claim 1, furthercomprising: receiving, from the application, spatial positioninginformation corresponding to a location of the mobile device.
 4. Amethod according to claim 1, wherein the audio interface corresponds toa microphone, the imaging interface corresponds to a camera, and thesignal relates to acoustics or one or more images of an environment ofthe mobile device.
 5. A method according to claim 1, further comprising:receiving the signal over a wireless network; and presenting the signalor information corresponding to the signal via a networked interface. 6.A method according to claim 1, further comprising: receiving anotherrequest to deactivate the mobile device; and generating another controlsignal, wherein the another control signal at least causes a memory ofthe mobile device to be erased.
 7. A method according to claim 6,further comprising: receiving an image of the memory before the memoryis erased; and storing the image to a networked repository.
 8. A methodaccording to claim 1, further comprising: monitoring transmissionsassociated with the mobile device; and storing information correspondingto the transmissions to a networked repository.
 9. A method according toclaim 1, further comprising: receiving another request to transmit thesignal or information corresponding to the signal to an administrativeagency; generating a report including the signal or the information; andtransmitting the report to the administrative agency.
 10. An apparatuscomprising: a communication interface configured to receive a request totrack a mobile device; and a processor configured to generate, inresponse to the request, a control signal to remotely activate anapplication on the mobile device for controlling an audio interface oran imaging interface of the mobile device to capture a signal from theaudio interface or the imaging interface.
 11. An apparatus according toclaim 10, wherein the communication interface is further configured totransmit the control signal to the mobile device over a wireless networkas part of a short messaging service message.
 12. An apparatus accordingto claim 10, wherein the communication interface is further configuredto receive, from the application, spatial positioning informationcorresponding to a location of the mobile device.
 13. An apparatusaccording to claim 10, wherein the communication interface is furtherconfigured to receive the signal over a wireless network and theprocessor is further configured to present the signal or informationcorresponding to the signal via a networked interface.
 14. An apparatusaccording to claim 10, wherein the communication interface is furtherconfigured to receive another request to deactivate the mobile deviceand the processor is further configured to generate another controlsignal, the another control signal being configured to at least cause amemory of the mobile device to be erased.
 15. An apparatus according toclaim 14, wherein the communication interface is further configured toreceive an image of the memory before the memory is erased and store theimage to a networked repository.
 16. An apparatus according to claim 10,further comprising: a module configured to monitor transmissionsassociated with the mobile device and to store information correspondingto the transmissions to a networked repository.
 17. An apparatusaccording to claim 10, wherein the processor is further configured togenerate a report including the signal or information corresponding tothe signal based on a request, received via the communication interface,to transmit the report to an administrative agency, and thecommunication interface is further configured to transmit the report tothe administrative agency.
 18. A method comprising: receiving, at amobile device, a control signal configured to remotely activate anapplication stored to the mobile device, wherein the application isconfigured to control an audio interface or an imaging interface of themobile device; and executing the application based on the control signalto capture a signal from the audio interface or the imaging interface.19. A method according to claim 18, wherein the control signal isreceived over a wireless network as part of a short messaging servicemessage.
 20. A method according to claim 18, further comprising:transmitting, over a wireless network, the signal captured from theaudio interface or the imaging interface to a tracking platform.